Downlink Control Information Activating a Cell and a Bandwidth Part

ABSTRACT

A wireless device receives configuration parameters of a cell. The configuration parameters comprise bandwidth part (BWP) parameters of: a first BWP and a default BWP; a first timer value associated with a cell deactivation timer; and a second timer value associated with a BWP inactivity timer. A downlink control information (DCI) indicating an activation of the cell is received. In response to the DCI: the cell is activated; and the cell deactivation timer is started based on the first timer value. In response to the activation of the cell, the first BWP of the cell is activated. The BWP inactivity timer is started based on the second timer value. In response to expiry of the BWP inactivity timer, a switch is made from the first BWP to the default BWP as an active BWP.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/171,731, filed Oct. 26, 2018, now U.S. Pat. No. 10,887,073, whichclaims the benefit of U.S. Provisional Application No. 62/577,239, filedOct. 26, 2017, which is hereby incorporated by reference in itsentirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentdisclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network and base stations as per an aspect of an embodiment of thepresent disclosure.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present disclosure.

FIG. 15 is an example diagram for synchronization signal blocktransmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 16 is an example diagram of random access procedure when configuredwith multiple beam as per an aspect of an embodiment of the presentdisclosure.

FIG. 17 is an example diagram for channel state information referencesignal (CSI-RS) transmissions as per an aspect of an embodiment of thepresent disclosure.

FIG. 18 is an example diagram for channel state information referencesignal (CSI-RS) transmissions as per an aspect of an embodiment of thepresent disclosure.

FIG. 19 is an example diagram for downlink beam management procedures asper an aspect of an embodiment of the present disclosure.

FIG. 20A is an example diagram for downlink beam failure scenario in atransmission receiving point (TRP) as per an aspect of an embodiment ofthe present disclosure.

FIG. 20B is an example diagram for downlink beam failure scenario inmultiple TRPs as per an aspect of an embodiment of the presentdisclosure.

FIG. 21A is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 21B is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 22A is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 22B is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 23 is an example diagram for downlink control information (DCI)formats as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example diagram for bandwidth part (BWP) configurations asper an aspect of an embodiment of the present disclosure.

FIG. 25 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 26 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 27 is an example diagram for timing management of BWP operation asper an aspect of an embodiment of the present disclosure.

FIG. 28 is an example diagram for flowchart of timing management of BWPoperation as per an aspect of an embodiment of the present disclosure.

FIG. 29 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 30 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 31 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 32 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal timing in a multicarrier communication system.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit BPSK binary phase shiftkeying CA carrier aggregation CSI channel state information CDMA codedivision multiple access CSS common search space CPLD complexprogrammable logic devices CC component carrier CP cyclic prefix DLdownlink DCI downlink control information DC dual connectivity eMBBenhanced mobile broadband EPC evolved packet core E-UTRANevolved-universal terrestrial radio access network FPGA fieldprogrammable gate arrays FDD frequency division multiplexing HDLhardware description languages HARQ hybrid automatic repeat request IEinformation element LTE long term evolution MCG master cell group MeNBmaster evolved node B MIB master information block MAC media accesscontrol MAC media access control MME mobility management entity mMTCmassive machine type communications NAS non-access stratum NR new radioOFDM orthogonal frequency division multiplexing PDCP packet dataconvergence protocol PDU packet data unit PHY physical PDCCH physicaldownlink control channel PHICH physical HARQ indicator channel PUCCHphysical uplink control channel PUSCH physical uplink shared channelPCell primary cell PCell primary cell PCC primary component carrierPSCell primary secondary cell pTAG primary timing advance group QAMquadrature amplitude modulation QPSK quadrature phase shift keying RBGresource block groups RLC radio link control RRC radio resource controlRA random access RB resource blocks SCC secondary component carrierSCell secondary cell SCG secondary cell group SeNB secondary evolvednode B sTAGs secondary timing advance group SDU service data unit S-GWserving gateway SRB signaling radio bearer SC-OFDM single carrier-OFDMSFN system frame number SIB system information block TAI tracking areaidentifier TAT time alignment timer TDD time division duplexing TDMAtime division multiple access TA timing advance TAG timing advance groupTTI transmission time interval TB transport block UL uplink UE userequipment URLLC ultra-reliable low-latency communications VHDL VHSIChardware description language CU central unit DU distributed unit Fs-CFs-control plane Fs-U Fs-user plane gNB next generation node B NGC nextgeneration core NG CP next generation control plane core NG-C NG-controlplane NG-U NG-user plane NR new radio NR MAC new radio MAC NR PHY newradio physical NR PDCP new radio PDCP NR RLC new radio RLC NR RRC newradio RRC NSSAI network slice selection assistance information PLMNpublic land mobile network UPGW user plane gateway Xn-C Xn-control planeXn-U Xn-user plane Xx-C Xx-control plane Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) maycomprise of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for an antenna port,and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for an antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in codewordsto be transmitted on a physical channel; modulation of scrambled bits togenerate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present disclosure. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentdisclosure. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC_CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three examples ofbearers, including, an MCG bearer, an SCG bearer and a split bearer asshown in FIG. 6. NR RRC may be located in master gNB and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster gNB. Multi-connectivity may also be described as having at leastone bearer configured to use radio resources provided by the secondarygNB. Multi-connectivity may or may not be configured/implemented inexample embodiments of the disclosure.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g., based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG SCell addition, the master gNB may provide the latestmeasurement results for the SCG cell(s); both a master gNB and secondarygNBs may know the SFN and subframe offset of each other by OAM, (e.g.,for the purpose of DRX alignment and identification of a measurementgap). In an example, when adding a new SCG SCell, dedicated NR RRCsignaling may be used for sending required system information of thecell as for CA, except for the SFN acquired from a MIB of the PSCell ofa SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprisesPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 900 to activate anSCell. A preamble 902 (Msg1) may be sent by a UE in response to a PDCCHorder 901 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 903 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 904 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an SCell by removing (releasing) the SCell and adding (configuring) anew SCell (with the same physical cell ID and frequency) with an updatedTAG ID. The new SCell with the updated TAG ID may initially be inactivesubsequent to being assigned the updated TAG ID. The eNB may activatethe updated new SCell and start scheduling packets on the activatedSCell. In an example implementation, it may not be possible to changethe TAG associated with an SCell, but rather, the SCell may need to beremoved and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running. A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.The tight interworking may enable a multiple RX/TX UE in RRC_CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e)LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three example bearers including an MCG bearer,an SCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, andFIG. 12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the disclosure.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g., based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure, or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present disclosure. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, a DU may be configured with a differentsplit, and a CU may provide different split options for different DUs.In per UE split, a gNB (CU and DU) may provide different split optionsfor different UEs. In per bearer split, different split options may beutilized for different bearer types. In per slice splice, differentsplit options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured, and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or a NGC (e.g. NG CP). Theslice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

A New Radio (NR) system may support both single beam and multi-beamoperations. In a multi-beam system, a base station (e.g., gNB) mayperform a downlink beam sweeping to provide coverage for downlinkSynchronization Signals (SSs) and common control channels. A UserEquipment (UE) may perform an uplink beam sweeping for uplink directionto access a cell. In a single beam scenario, a gNB may configuretime-repetition transmission for one SS block, which may comprise atleast Primary Synchronization Signal (PSS), Secondary SynchronizationSignal (SSS), and Physical Broadcast Channel (PBCH), with a wide beam.In a multi-beam scenario, a gNB may configure at least some of thesesignals and physical channels in multiple beams. A UE may identify atleast OFDM symbol index, slot index in a radio frame and radio framenumber from an SS block.

In an example, in an RRC_INACTIVE state or RRC_IDLE state, a UE mayassume that SS blocks form an SS burst, and an SS burst set. An SS burstset may have a given periodicity. In multi-beam scenarios, SS blocks maybe transmitted in multiple beams, together forming an SS burst. One ormore SS blocks may be transmitted on one beam. A beam has a steeringdirection. If multiple SS bursts are transmitted with beams, these SSbursts together may form an SS burst set as shown in FIG. 15. A basestation 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to 1502Hduring time periods 1503. A plurality of these SS bursts may comprise anSS burst set, such as an SS burst set 1504 (e.g., SS bursts 1502A and1502E). An SS burst set may comprise any number of a plurality of SSbursts 1502A to 1502H. Each SS burst within an SS burst set maytransmitted at a fixed or variable periodicity during time periods 1503.

An SS may be based on Cyclic Prefix-Orthogonal Frequency DivisionMultiplexing (CP-OFDM). The SS may comprise at least two types ofsynchronization signals; NR-PSS (Primary synchronization signal) andNR-SSS (Secondary synchronization signal). NR-PSS may be defined atleast for initial symbol boundary synchronization to the NR cell. NR-SSSmay be defined for detection of NR cell ID or at least part of NR cellID. NR-SSS detection may be based on the fixed time/frequencyrelationship with NR-PSS resource position irrespective of duplex modeand beam operation type at least within a given frequency range and CPoverhead. Normal CP may be supported for NR-PSS and NR-SSS.

The NR may comprise at least one physical broadcast channel (NR-PBCH).When a gNB transmit (or broadcast) the NR-PBCH, a UE may decode theNR-PBCH based on the fixed relationship with NR-PSS and/or NR-SSSresource position irrespective of duplex mode and beam operation type atleast within a given frequency range and CP overhead. NR-PBCH may be anon-scheduled broadcast channel carrying at least a part of minimumsystem information with fixed payload size and periodicity predefined inthe specification depending on carrier frequency range.

In single beam and multi-beam scenarios, NR may comprise an SS blockthat may support time (frequency, and/or spatial) division multiplexingof NR-PSS, NR-SSS, and NR-PBCH. A gNB may transmit NR-PSS, NR-SSS and/orNR-PBCH within an SS block. For a given frequency band, an SS block maycorrespond to N OFDM symbols based on the default subcarrier spacing,and N may be a constant. The signal multiplexing structure may be fixedin NR. A wireless device may identify, e.g., from an SS block, an OFDMsymbol index, a slot index in a radio frame, and a radio frame numberfrom an SS block.

A NR may support an SS burst comprising one or more SS blocks. An SSburst set may comprise one or more SS bursts. For example, a number ofSS bursts within a SS burst set may be finite. From physical layerspecification perspective, NR may support at least one periodicity of SSburst set. From UE perspective, SS burst set transmission may beperiodic, and UE may assume that a given SS block is repeated with an SSburst set periodicity.

Within an SS burst set periodicity, NR-PBCH repeated in one or more SSblocks may change. A set of possible SS block time locations may bespecified per frequency band in an RRC message. The maximum number ofSS-blocks within SS burst set may be carrier frequency dependent. Theposition(s) of actual transmitted SS-blocks may be informed at least forhelping CONNECTED/IDLE mode measurement, for helping CONNECTED mode UEto receive downlink (DL) data/control in one or more SS-blocks, or forhelping IDLE mode UE to receive DL data/control in one or moreSS-blocks. A UE may not assume that the gNB transmits the same number ofphysical beam(s). A UE may not assume the same physical beam(s) acrossdifferent SS-blocks within an SS burst set. For an initial cellselection, UE may assume default SS burst set periodicity which may bebroadcast via an RRC message and frequency band-dependent. At least formulti-beams operation case, the time index of SS-block may be indicatedto the UE.

For CONNECTED and IDLE mode UEs, NR may support network indication of SSburst set periodicity and information to derive measurementtiming/duration (e.g., time window for NR-SS detection). A gNB mayprovide (e.g., via broadcasting an RRC message) one SS burst setperiodicity information per frequency carrier to UE and information toderive measurement timing/duration if possible. In case that one SSburst set periodicity and one information regarding timing/duration areindicated, a UE may assume the periodicity and timing/duration for allcells on the same carrier. If a gNB does not provide indication of SSburst set periodicity and information to derive measurementtiming/duration, a UE may assume a predefined periodicity, e.g., 5 ms,as the SS burst set periodicity. NR may support set of SS burst setperiodicity values for adaptation and network indication.

For initial access, a UE may assume a signal corresponding to a specificsubcarrier spacing of NR-PSS/SSS in a given frequency band given by a NRspecification. For NR-PSS, a Zadoff-Chu (ZC) sequence may be employed asa sequence for NR-PSS. NR may define at least one basic sequence lengthfor a SS in case of sequence-based SS design. The number of antenna portof NR-PSS may be 1. For NR-PBCH transmission, NR may support a fixednumber of antenna port(s). A UE may not be required for a blinddetection of NR-PBCH transmission scheme or number of antenna ports. AUE may assume the same PBCH numerology as that of NR-SS. For the minimumsystem information delivery, NR-PBCH may comprise a part of minimumsystem information. NR-PBCH contents may comprise at least a part of theSFN (system frame number) or CRC. A gNB may transmit the remainingminimum system information in shared downlink channel via NR-PDSCH.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may berepeated for a cell, e.g., to support cell selection, cell reselection,and/or initial access procedures. For an SS burst, an associated PBCH ora physical downlink shared channel (PDSCH) scheduling system informationmay be broadcasted by a base station to multiple wireless devices. ThePDSCH may be indicated by a physical downlink control channel (PDCCH) ina common search space. The system information may comprise a physicalrandom access channel (PRACH) configuration for a beam. For a beam, abase station (e.g., a gNB in NR) may have a RACH configuration which mayinclude a PRACH preamble pool, time and/or frequency radio resources,and other power related parameters. A wireless device may use a PRACHpreamble from a RACH configuration to initiate a contention-based RACHprocedure or a contention-free RACH procedure. A wireless device mayperform a 4-step RACH procedure, which may be a contention-based RACHprocedure or a contention-free RACH procedure. The wireless device mayselect a beam associated with an SS block that may have the bestreceiving signal quality. The wireless device may successfully detect acell identifier associated with the cell and decode system informationwith a RACH configuration. The wireless device may use one PRACHpreamble and select one PRACH resource from RACH resources indicated bythe system information associated with the selected beam. A PRACHresource may comprise at least one of: a PRACH index indicating a PRACHpreamble, a PRACH format, a PRACH numerology, time and/or frequencyradio resource allocation, power setting of a PRACH transmission, and/orother radio resource parameters. For a contention-free RACH procedure,the PRACH preamble and resource may be indicated in a DCI or other highlayer signaling.

FIG. 16 shows an example of a random access procedure (e.g., via a RACH)that may include sending, by a base station, one or more SS blocks. Awireless device 1620 (e.g., a UE) may transmit one or more preambles toa base station 1621 (e.g., a gNB in NR). Each preamble transmission bythe wireless device may be associated with a separate random accessprocedure, such as shown in FIG. 16. The random access procedure maybegin at step 1601 with a base station 1621 (e.g., a gNB in NR) sendinga first SS block to a wireless device 1621 (e.g., a UE). Any of the SSblocks may comprise one or more of a PSS, SSS, tertiary synchronizationsignal (TSS), or PBCH signal. The first SS block in step 1601 may beassociated with a first PRACH configuration. At step 1602, the basestation 1621 may send to the wireless device 1620 a second SS block thatmay be associated with a second PRACH configuration. At step 1603, thebase station 1621 may send to the wireless device 1620 a third SS blockthat may be associated with a third PRACH configuration. At step 1604,the base station 1621 may send to the wireless device 1620 a fourth SSblock that may be associated with a fourth PRACH configuration. Anynumber of SS blocks may be sent in the same manner in addition to, orreplacing, steps 1603 and 1604. An SS burst may comprise any number ofSS blocks. For example, SS burst 1610 comprises the three SS blocks sentduring steps 1602-1604.

The wireless device 1620 may send to the base station 1621 a preamble,at step 1605, e.g., after or in response to receiving one or more SSblocks or SS bursts. The preamble may comprise a PRACH preamble, and maybe referred to as RA Msg 1. The PRACH preamble may be transmitted instep 1605 according to or based on a PRACH configuration that may bereceived in an SS block (e.g., one of the SS blocks from steps1601-1604) that may be determined to be the best SS block beam. Thewireless device 1620 may determine a best SS block beam from among SSblocks it may receive prior to sending the PRACH preamble. The basestation 1621 may send a random access response (RAR), which may bereferred to as RA Msg2, at step 1606, e.g., after or in response toreceiving the PRACH preamble. The RAR may be transmitted in step 1606via a DL beam that corresponds to the SS block beam associated with thePRACH configuration. The base station 1621 may determine the best SSblock beam from among SS blocks it previously sent prior to receivingthe PRACH preamble. The base station 1621 may receive the PRACH preambleaccording to or based on the PRACH configuration associated with thebest SS block beam.

The wireless device 1620 may send to the base station 1621 anRRCConnectionRequest and/or RRCConnectionResumeRequest message, whichmay be referred to as RA Msg3, at step 1607, e.g., after or in responseto receiving the RAR. The base station 1621 may send to the wirelessdevice 1620 an RRCConnectionSetup and/or RRCConnectionResume message,which may be referred to as RA Msg4, at step 1608, e.g., after or inresponse to receiving the RRCConnectionRequest and/orRRCConnectionResumeRequest message. The wireless device 1620 may send tothe base station 1621 an RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message, which may be referred to as RAMsg5, at step 1609, e.g., after or in response to receiving theRRCConnectionSetup and/or RRCConnectionResume. An RRC connection may beestablished between the wireless device 1620 and the base station 1621,and the random access procedure may end, e.g., after or in response toreceiving the RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may bedetermined based on a channel state information reference signal(CSI-RS). A wireless device may use a CSI-RS in a multi-beam system forestimating the beam quality of the links between the wireless device anda base station. For example, based on a measurement of a CSI-RS, awireless device may report CSI for downlink channel adaption. A CSIparameter may include a precoding matrix index (PMI), a channel qualityindex (CQI) value, and/or a rank indicator (RI). A wireless device mayreport a beam index based on a reference signal received power (RSRP)measurement on a CSI-RS. The wireless device may report the beam indexin a CSI resource indication (CRI) for downlink beam selection. A basestation may transmit a CSI-RS via a CSI-RS resource, such as via one ormore antenna ports, or via one or more time and/or frequency radioresources. A beam may be associated with a CSI-RS. A CSI-RS may comprisean indication of a beam direction. Each of a plurality of beams may beassociated with one of a plurality of CSI-RSs. A CSI-RS resource may beconfigured in a cell-specific way, e.g., via common RRC signaling.Additionally or alternatively, a CSI-RS resource may be configured in awireless device-specific way, e.g., via dedicated RRC signaling and/orlayer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices inor served by a cell may measure a cell-specific CSI-RS resource. Adedicated subset of wireless devices in or served by a cell may measurea wireless device-specific CSI-RS resource. A base station may transmita CSI-RS resource periodically, using aperiodic transmission, or using amulti-shot or semi-persistent transmission. In a periodic transmission,a base station may transmit the configured CSI-RS resource using aconfigured periodicity in the time domain. In an aperiodic transmission,a base station may transmit the configured CSI-RS resource in adedicated time slot. In a multi-shot or semi-persistent transmission, abase station may transmit the configured CSI-RS resource in a configuredperiod. A base station may configure different CSI-RS resources indifferent terms for different purposes. Different terms may include,e.g., cell-specific, device-specific, periodic, aperiodic, multi-shot,or other terms. Different purposes may include, e.g., beam management,CQI reporting, or other purposes.

FIG. 17 shows an example of transmitting CSI-RSs periodically for abeam. A base station 1701 may transmit a beam in a predefined order inthe time domain, such as during time periods 1703. Beams used for aCSI-RS transmission, such as for CSI-RS 1704 in transmissions 1702Cand/or 1703E, may have a different beam width relative to a beam widthfor SS-blocks transmission, such as for SS blocks 1702A, 1702B, 1702D,and 1702F-1702H. Additionally or alternatively, a beam width of a beamused for a CSI-RS transmission may have the same value as a beam widthfor an SS block. Some or all of one or more CSI-RSs may be included inone or more beams. An SS block may occupy a number of OFDM symbols(e.g., 4), and a number of subcarriers (e.g., 240), carrying asynchronization sequence signal. The synchronization sequence signal mayidentify a cell.

FIG. 18 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 18 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 18 shows three beams that may be configured for a wireless device,e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in a RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin a RB of a third symbol. All subcarriers in a RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs), such as shown in FIG. 20A and FIG. 20B,respectively.

FIG. 19 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), e.g., tosupport a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, e.g., anintra-TRP and/or inter-TRP Tx beam sweep from a set of different beams(shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device 1901, may include, e.g., a wireless device Rx beamsweep from a set of different beams (shown, in the bottom rows of P1 andP3, as ovals rotated in a clockwise direction indicated by the dashedarrow). Procedure P2 may be used to enable a wireless device measurementon different Tx beams of a TRP (or multiple TRPs) (shown, in the top rowof P2, as ovals rotated in a counter-clockwise direction indicated bythe dashed arrow), e.g., which may change inter-TRP and/or intra-TRP Txbeam(s). Procedure P2 may be performed, e.g., on a smaller set of beamsfor beam refinement than in procedure P1. P2 may be a particular exampleof P1. Procedure P3 may be used to enable a wireless device measurementon the same Tx beam (shown as oval in P3), e.g., to change a wirelessdevice Rx beam if the wireless device 1901 uses beamforming.

A wireless device 1901 (e.g., a UE) and/or a base station 1902 (e.g., agNB) may trigger a beam failure recovery mechanism. The wireless device1901 may trigger a beam failure recovery (BFR) request transmission,e.g., if a beam failure event occurs. A beam failure event may include,e.g., a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory. A determination of anunsatisfactory quality of beam pair link(s) of an associated channel maybe based on the quality falling below a threshold and/or an expirationof a timer.

The wireless device 1901 may measure a quality of beam pair link(s)using one or more reference signals (RS). One or more SS blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. Each of the one or more CSI-RS resources may be associatedwith a CSI-RS resource index (CRI). A quality of a beam pair link may bebased on one or more of an RSRP value, reference signal received quality(RSRQ) value, and/or CSI value measured on RS resources. The basestation 1902 may indicate that an RS resource, e.g., that may be usedfor measuring a beam pair link quality, is quasi-co-located (QCLed) withone or more DM-RSs of a control channel. The RS resource and the DM-RSsof the control channel may be QCLed when the channel characteristicsfrom a transmission via an RS to the wireless device 1901, and thechannel characteristics from a transmission via a control channel to thewireless device, are similar or the same under a configured criterion.

FIG. 20A shows an example of a beam failure event involving a singleTRP. A single TRP such as at a base station 2001 may transmit, to awireless device 2002, a first beam 2003 and a second beam 2004. A beamfailure event may occur if, e.g., a serving beam, such as the secondbeam 2004, is blocked by a moving vehicle 2005 or other obstruction(e.g., building, tree, land, or any object) and configured beams (e.g.,the first beam 2003 and/or the second beam 2004), including the servingbeam, are received from the single TRP. The wireless device 2002 maytrigger a mechanism to recover from beam failure when a beam failureoccurs.

FIG. 20B shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 2006 and at asecond base station 2009, may transmit, to a wireless device 2008, afirst beam 2007 (e.g., from the first base station 2006) and a secondbeam 2010 (e.g., from the second base station 2009). A beam failureevent may occur when, e.g., a serving beam, such as the second beam2010, is blocked by a moving vehicle 2011 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 2007 and/or the second beam 2010) are received from multipleTRPs. The wireless device 2008 may trigger a mechanism to recover frombeam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M≥1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channel.Signaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, e.g.,via an uplink physical channel or signal, a base station may detect thatthere is a beam failure event, for the wireless device, by monitoringthe uplink physical channel or signal. The base station may initiate abeam recovery mechanism to recover the beam pair link for transmittingPDCCH between the base station and the wireless device. The base stationmay transmit one or more control signals, to the wireless device, e.g.,after or in response to receiving the beam failure recovery request. Abeam recovery mechanism may be, e.g., an L1 scheme, or a higher layerscheme.

A base station may transmit one or more messages comprising, e.g.,configuration parameters of an uplink physical channel and/or a signalfor transmitting a beam failure recovery request. The uplink physicalchannel and/or signal may be based on at least one of the following: anon-contention based PRACH (e.g., a beam failure recovery PRACH orBFR-PRACH), which may use a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

A gNB may respond a confirmation message to a UE after receiving one ormultiple BFR request. The confirmation message may include the CRIassociated with the candidate beam the UE indicates in the one ormultiple BFR request. The confirmation message may be a L1 controlinformation.

Secondary Cell Activation/Deactivation Mechanism

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells).

When configured with CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a gNB may transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). In anexample, a wireless device may deactivate an SCell in response to anexpiry of the SCell timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising: SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell. The wireless devicemay start or restart the first SCell timer in the slot when the SCellActivation/Deactivation MAC CE activating the SCell has been received.In an example, in response to the activating the SCell, the wirelessdevice may (re-)initialize one or more suspended configured uplinkgrants of a configured grant Type 1 associated with the SCell accordingto a stored configuration. In an example, in response to the activatingthe SCell, the wireless device may trigger PHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart a first SCell timer (e.g., sCellDeactivationTimer)associated with the activated SCell. In an example, when at least onesecond PDCCH on a serving cell (e.g. a PCell or an SCell configured withPUCCH, i.e. PUCCH SCell) scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell, awireless device may restart the first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell.

In an example, when an SCell is deactivated, if there may be an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

FIG. 21A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’)may identify the SCell Activation/Deactivation MAC CE of one octet. TheSCell Activation/Deactivation MAC CE of one octet may have a fixed size.The SCell Activation/Deactivation MAC CE of one octet may comprise asingle octet. The single octet may comprise a first number of C-fields(e.g. seven) and a second number of R-fields (e.g., one).

FIG. 21B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’) may identify the SCell Activation/Deactivation MAC CE of fouroctets. The SCell Activation/Deactivation MAC CE of four octets may havea fixed size. The SCell Activation/Deactivation MAC CE of four octetsmay comprise four octets. The four octets may comprise a third number ofC-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

In FIG. 21A and/or FIG. 21B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 21A and FIG. 21B, an R field may indicate a reserved bit.The R field may be set to zero.

FIG. 22A and FIG. 22B show timeline when a UE receives a MAC activationcommand. When a UE receives a MAC activation command for a secondarycell in subframe n, the corresponding actions in the MAC layer shall beapplied no later than the minimum requirement defined in 3GPP TS 36.133or TS 38.133 and no earlier than subframe n+8, except for the following:the actions related to CSI reporting and the actions related to thesCellDeactivationTimer associated with the secondary cell, which shallbe applied in subframe n+8. When a UE receives a MAC deactivationcommand for a secondary cell or the sCellDeactivationTimer associatedwith the secondary cell expires in subframe n, the corresponding actionsin the MAC layer shall apply no later than the minimum requirementdefined in 3GPP TS 36.133 or TS 38.133, except for the actions relatedto CSI reporting which shall be applied in subframe n+8.

When a UE receives a MAC activation command for a secondary cell insubframe n, the actions related to CSI reporting and the actions relatedto the sCellDeactivationTimer associated with the secondary cell, areapplied in subframe n+8. When a UE receives a MAC deactivation commandfor a secondary cell or other deactivation conditions are met (e.g. thesCellDeactivationTimer associated with the secondary cell expires) insubframe n, the actions related to CSI reporting are applied in subframen+8. The UE starts reporting invalid or valid CSI for the Scell at the(n+8)^(th) subframe, and start or restart the sCellDeactivationTimerwhen receiving the MAC CE activating the SCell in the n^(th) subframe.For some UE having slow activation, it may report an invalid CSI(out-of-range CSI) at the (n+8)^(th) subframe, for some UE having aquick activation, it may report a valid CSI at the (n+8)^(th) subframe.

When a UE receives a MAC activation command for an SCell in subframe n,the UE starts reporting CQI/PMI/RI/PTI for the SCell at subframe n+8 andstarts or restarts the sCellDeactivationTimer associated with the SCellat subframe n+8. It is important to define the timing of these actionsfor both UE and eNB. For example, sCellDeactivationTimer is maintainedin both eNB and UE and it is important that both UE and eNB stop, startand/or restart this timer in the same TTI. Otherwise, thesCellDeactivationTimer in the UE may not be in-sync with thecorresponding sCellDeactivationTimer in the eNB. Also, eNB startsmonitoring and receiving CSI (CQI/PMI/RI/PTI) according to thepredefined timing in the same TTI and/or after UE starts transmittingthe CSI. If the CSI timings in UE and eNB are not coordinated based on acommon standard or air interface signaling the network operation mayresult in inefficient operations and/or errors.

Example of Downlink Control Information (DCI)

FIG. 23 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In an example, a gNB may transmit a DCI via a PDCCH forscheduling decision and power-control commends. More specifically, theDCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

The different types of control information correspond to different DCImessage sizes. For example, supporting spatial multiplexing withnoncontiguous allocation of RBs in the frequency domain may require alarger scheduling message in comparison with an uplink grant allowingfor frequency-contiguous allocation only. The DCI may be categorizedinto different DCI formats, where a format corresponds to a certainmessage size and usage.

In an example, a UE may monitor one or more PDCCH to detect one or moreDCI with one or more DCI format. The one or more PDCCH may betransmitted in common search space or UE-specific search space. A UE maymonitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the information in the DCI formats used for downlinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In a NR system, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets. A gNB maytransmit one or more RRC message comprising configuration parameters ofone or more control resource sets. At least one of the one or morecontrol resource sets may comprise at least one of: a first OFDM symbol;a number of consecutive OFDM symbols; a set of resource blocks; aCCE-to-REG mapping; and a REG bundle size, in case of interleavedCCE-to-REG mapping.

Example of Bandwidth Part Management

FIG. 24 shows example of multiple BWP configuration. A gNB may transmitone or more message comprising configuration parameters of one or morebandwidth parts (BWP). The one or more BWPs may have differentnumerologies. A gNB may transmit one or more control information forcross-BWP scheduling to a UE. One BWP may overlap with another BWP infrequency domain.

A gNB may transmit one or more messages comprising configurationparameters of one or more DL and/or UL BWPs for a cell, with at leastone BWP as the active DL or UL BWP, and zero or one BWP as the defaultDL or UL BWP. For the PCell, the active DL BWP may be the DL BWP onwhich the UE may monitor one or more PDCCH, and/or receive PDSCH. Theactive UL BWP is the UL BWP on which the UE may transmit uplink signal.For a secondary cell (SCell) if configured, the active DL BWP may be theDL BWP on which the UE may monitor one or more PDCCH and receive PDSCHwhen the SCell is activated by receiving a MAC activation/deactivationCE. The active UL BWP is the UL BWP on which the UE may transmit PUCCH(if configured) and/or PUSCH when the SCell is activated by receiving aMAC activation/deactivation CE. Configuration of multiple BWPs may beused to save UE's power consumption. When configured with an active BWPand a default BWP, a UE may switch to the default BWP if there is noactivity on the active BWP. For example, a default BWP may be configuredwith narrow bandwidth, an active BWP may be configured with widebandwidth. If there is no signal transmitting or receiving, the UE mayswitch the BWP to the default BWP, which may reduce power consumption.

Switching BWP may be triggered by a DCI or a timer. When a UE receives aDCI indicating DL BWP switching from an active BWP to a new BWP, the UEmay monitor PDCCH and/or receive PDSCH on the new BWP. When the UEreceives a DCI indicating UL BWP switching from an active BWP to a newBWP, the UE may transmit PUCCH (if configured) and/or PUSCH on the newBWP. A gNB may transmit one or more messages comprising a BWP inactivitytimer to a UE. The UE starts the timer when it switches its active DLBWP to a DL BWP other than the default DL BWP. The UE may restart thetimer to the initial value when it successfully decodes a DCI toschedule PDSCH(s) in its active DL BWP. The UE may switch its active DLBWP to the default DL BWP when the BWP timer expires.

In an example embodiment, a UE configured for operation in bandwidthparts (BWPs) of a serving cell, may be configured by higher layers forthe serving cell a set of bandwidth parts (BWPs) for receptions by theUE (DL BWP set) or a set of BWPs for transmissions by the UE (UL BWPset). In an example, for a DL BWP or UL BWP in a set of DL BWPs or ULBWPs, respectively, the UE may be configured at least one of followingfor the serving cell: a subcarrier spacing for DL and/or UL provided byhigher layer parameter, a cyclic prefix for DL and/or UL provided byhigher layer parameter, a number of contiguous PRBs for DL and/or ULprovided by higher layer parameter, an offset of the first PRB for DLand/or UL in the number of contiguous PRBs relative to the first PRB byhigher layer, or Q control resource sets if the BWP is a DL BWP.

In an example embodiment, for each serving cell, higher layer signalingmay configure a UE with Q control resource sets. In an example, forcontrol resource set q, 0≤q<Q, the configuration may comprise at leastone of following: a first OFDM symbol provided by one or more higherlayer parameters, a number of consecutive OFDM symbols provided by oneor more higher layer parameters, a set of resource blocks provided byone or more higher layer parameters, a CCE-to-REG mapping provided byone or more higher layer parameters, a REG bundle size, in case ofinterleaved CCE-to-REG mapping, provided by one or more higher layerparameters, or antenna port quasi-collocation provided by higher layerparameter.

In an example embodiment, a control resource set may comprise a set ofCCEs numbered from 0 to N_(CCE,q)−1 where N_(CCE,q) may be the number ofCCEs in control resource set q.

In an example embodiment, the sets of PDCCH candidates that a UEmonitors may be defined in terms of PDCCH UE-specific search spaces. APDCCH UE-specific search space at CCE aggregation level L∈{1, 2, 4, 8}may be defined by a set of PDCCH candidates for CCE aggregation level L.In an example, for a DCI format, a UE may be configured per serving cellby one or more higher layer parameters a number of PDCCH candidates perCCE aggregation level L.

In an example embodiment, in non-DRX mode operation, a UE may monitorone or more PDCCH candidate in control resource set q according to aperiodicity of W_(PDCCH,q) symbols that may be configured by one or morehigher layer parameters for control resource set q.

In an example embodiment, if a UE is configured with higher layerparameter, e.g., cif-InSchedulingCell, the carrier indicator field valuemay correspond to cif-InSchedulingCell.

In an example embodiment, for the serving cell on which a UE may monitorone or more PDCCH candidate in a UE-specific search space, if the UE isnot configured with a carrier indicator field, the UE may monitor theone or more PDCCH candidates without carrier indicator field. In anexample, for the serving cell on which a UE may monitor one or morePDCCH candidates in a UE-specific search space, if a UE is configuredwith a carrier indicator field, the UE may monitor the one or more PDCCHcandidates with carrier indicator field.

In an example embodiment, a UE may not monitor one or more PDCCHcandidates on a secondary cell if the UE is configured to monitor one ormore PDCCH candidates with carrier indicator field corresponding to thatsecondary cell in another serving cell. For example, for the servingcell on which the UE may monitor one or more PDCCH candidates, the UEmay monitor the one or more PDCCH candidates at least for the sameserving cell.

In an example embodiment, a UE may receive PDCCH and PDSCH in a DL BWPaccording to a configured subcarrier spacing and CP length for the DLBWP. A UE may transmit PUCCH and PUSCH in an UL BWP according to aconfigured subcarrier spacing and CP length for the UL BWP.

In an example embodiment, a UE may be configured, by one or more higherlayer parameters, a DL BWP from a configured DL BWP set for DLreceptions. A UE may be configured by one or more higher layerparameters, an UL BWP from a configured UL BWP set for UL transmissions.If a DL BWP index field is configured in a DCI format scheduling PDSCHreception to a UE, the DL BWP index field value may indicate the DL BWP,from the configured DL BWP set, for DL receptions. If an UL-BWP indexfield is configured in a DCI format scheduling PUSCH transmission from aUE, the UL-BWP index field value may indicate the UL BWP, from theconfigured UL BWP set, for UL transmissions.

In an example embodiment, for TDD, a UE may expect that the centerfrequency for the DL BWP is same as the center frequency for the UL BWP.

In an example embodiment, a UE may not monitor PDCCH when the UEperforms measurements over a bandwidth that is not within the DL BWP forthe UE.

In an example embodiment, for an initial active DL BWP, UE may identifythe bandwidth and frequency of the initial active DL BWP in response toreceiving the NR-PBCH.

In an example embodiment, a bandwidth of an initial active DL BWP may beconfined within the UE minimum bandwidth for the given frequency band.For example, for flexible for DL information scheduling, the bandwidthmay be indicated in PBCH, and/or some bandwidth candidates may bepredefined. For example, x bits may be employed for indication. Thisenables.

In an example embodiment, a frequency location of initial active DL BWPmay be derived from the bandwidth and SS block, e.g. center frequency ofthe initial active DL BWP. For example, a SS block may have a frequencyoffset, as the edge of SS block PRB and data PRB boundary may not bealigned. Predefining the frequency location of SS block and initialactive DL BWP may reduce the PBCH payload size, additional bits are notneeded for indication of frequency location of initial active DL BWP.

In an example, for the paired UL BWP, the bandwidth and frequencylocation may be informed in RMSI.

In an example embodiment, for a UE, gNB may configure a set of BWPs byRRC. The UE may transmit or receive in an active BWP from the configuredBWPs in a given time instance. For example, an activation/deactivationof DL bandwidth part by means of timer for a UE to switch its active DLbandwidth part to a default DL bandwidth part may be supported. In thiscase, when the timer at the UE side expires, e.g. the UE has notreceived scheduling DCI for X ms, the UE may switch to the default DLBWP.

In an example, a new timer, e.g., BWPDeactivationTimer, may be definedto deactivate the original BWP and switch to the default BWP. TheBWPDeactivationTimer may be started when the original BWP is activatedby the activation/deactivation DCI. If PDCCH on the original BWP isreceived, a UE may restart the BWPDeactivationTimer associated with theoriginal BWP. For example, if the BWPDeactivationTimer expires, a UE maydeactivate the original BWP and switch to the default BWP, may stop theBWPDeactivationTimer for the original BWP, and may (or may not) flushall HARQ buffers associated with the original BWP.

In an example embodiment, gNB and UE may have different understanding ofthe starting of the timer since the UE may miss scheduling grants. In anexample, the UE may be triggered to switch to the default BWP, but gNBmay schedules the UE in the previous active BWP. For example, in thecase that the default BWP is nested within other BWPs, gNB may restrictthe location of the CORESET of BWP2 to be within BWP1 (e.g., the narrowband BWP1 may be the default BWP). Then the UE may receive CORESET andswitch back to BWP2 if it mistakenly switches to the default BWP.

In an example embodiment, for a case that the default BWP and the otherBWPs are not overlapped in frequency domain, it may not solve a missswitching problem by restricting the location of the CORESET. Forexample, the gNB may maintain a timer for a UE. When the timer expires,e.g. there is no data scheduling for the UE for Y ms, or gNB has notreceived feedback from the UE for Y′ ms, the UE may switch to thedefault BWP to send paging signal or re-schedule the UE in the defaultBWP.

In an example embodiment, gNB may not fix the default bandwidth part tobe the same as initial active bandwidth part it. Since the initialactive DL BWP may be the SS block bandwidth which is common to UEs inthe cell, the traffic load may be very heavy if many UEs fall back tosuch small bandwidth for data transmission. Configuring the UEs withdifferent default BWPs may help to balance the load in the systembandwidth.

In an example embodiment, on a Scell, there may be no initial active BWPsince the initial access is performed on the Pcell. For example, theinitially activated DL BWP and/or UL BWP when the Scell is activated maybe configured or reconfigured by RRC signaling. In an example, thedefault BWP of the Scell may also be configured or reconfigured by RRCsignaling. To strive for a unified design for both Pcell and Scell, thedefault BWP may be configured or reconfigured by the RRC signalling, andthe default BWP may be one of the configured BWPs of the UE.

In an example embodiment, gNB may configure UE-specific default DL BWPother than initial active BWP after RRC connection, e.g., for thepurpose of load balancing. The default BWP may support other connectedmode operations (besides operations supported by initial active BWP) forexample fall back and connected mode paging. In this case, the defaultBWP may comprise common search space, at least the search space neededfor monitoring the pre-emption indications. For example, for FDD, thedefault DL and UL BWPs may be independently configured to the UE.

In an example, the initial active DL/UL BWP may be set as default DL/ULBWP. In an example, a UE may return to default DL/UL BWP in some cases.For example, if a UE does not receive control for a long time, the UEmay fallback to default BWP.

In an example embodiment, gNB may configure UE with multiple BWPs. Forexample, the multiple BWPs may share at least one CORESET includingdefault BWP. For example, CORESET for RMSI may be shared for allconfigured BWP. Without going back to another BWP or default BWP, the UEmay receive control information via the common CORESET. To minimize theambiguity of resource allocation, the common CORESET may schedule datawithin only default BWP. For example, frequency region of default BWPmay belong to all the configured BWPs.

In an example embodiment, when the configured BWP is associated with adifferent numerology from default BWP, a semi-static pattern of BWPswitching to default BWP may be considered. For example, to check RMSIat least periodically, switching to default BWP may be considered. Thismay be necessary particularly when BWPs use different numerologies.

In an example embodiment, in terms of reconfiguration of default BWPfrom initial BWP, it may be considered for RRC connected UEs. For RRCIDLE UEs, default BWP may be same as initial BWP (or, RRC IDLE UE mayfallback to initial BWP regardless of default BWP). If a UE performsmeasurement based on SS block, reconfiguration of default BWP outside ofinitial BWP may become very inefficient due to frequent measurement gap.In this sense, if default BWP is reconfigured to outside of initial BWP,the following conditions may be satisfied: a UE is in CONNECTED mode,and a UE is not configured with SS block based measurement for bothserving cell and neighbor cells.

In an example embodiment, a DL BWP other than the initial active DL BWPmay be configured to a UE as the default DL BWP. The reconfiguring thedefault DL BWP may be due to load balancing and/or differentnumerologies employed for active DL BWP and initial active DL BWP.

In an example embodiment, a default BWP on Pcell may be an initialactive DL BWP for transmission of RMSI, comprising RMSI CORESET withCSS. The RMSI CORESET may comprise USS. The initial active/default BWPmay remain active BWP for the user also after UE becomes RRC connected.

In an example embodiment, for a paired spectrum, downlink and uplinkbandwidth parts may be independently activated while, for an unpairedspectrum downlink and uplink bandwidth parts are jointly activated. Incase of bandwidth adaptation, where the bandwidth of the active downlinkBWP may be changed, there may, in case of an unpaired spectrum, be ajoint activation of a new downlink BWP and new uplink BWP. For example,a new DL/UL BWP pair where the bandwidth of the uplink BWPs may be thesame (e.g., no change of uplink BWP).

In an example embodiment, there may be an association of DL BWP and ULBWP in RRC configuration. For example, in case of TDD, a UE may notretune the center frequency of channel BW between DL and UL. In thiscase, since the RF is shared between DL and UL in TDD, a UE may notretune the RF BW for every alternating DL-to-UL and UL-to-DL switching.

In an example embodiment, making an association between DL BWP and ULBWP may allow that one activation/deactivation command may switch bothDL and UL BWPs at once. Otherwise, separate BWP switching commands maybe necessary.

In an example embodiment, a DL BWP and a UL BWP may be configured to theUE separately. Pairing of the DL BWP and the UL BWP may imposeconstrains on the configured BWPs, e.g., the paired DL BWP and UL BWPmay be activated simultaneously. For example, gNB may indicate a DL BWPand a UL BWP to a UE for activation in a FDD system. In an example, gNBmay indicate a DL BWP and a UL BWP with the same center frequency to aUE for activation in a TDD system. Since the activation/deactivation ofthe BWP of the UE is instructed by gNB, no paring or association of theDL BWP and UL BWP may be mandatory even for TDD system. It may be up togNB implementation

In an example embodiment, the association between DL carrier and ULcarrier within a serving cell may be done by carrier association. Forexample, for TDD system, UE may not be expected to retune the centerfrequency of channel BW between DL and UL. To achieve it, an associationbetween DL BWP and UL BWP may be needed. For example, a way to associatethem may be to group DL BWP configurations with same center frequency asone set of DL BWPs and group UL BWP configurations with same centerfrequency as one set of UL BWPs. The set of DL BWPs may be associatedwith the set of UL BWPs sharing the same center frequency.

For an FDD serving cell, there may be no association between DL BWP andUL BWP if the association between DL carrier and UL carrier within aserving cell may be done by carrier association.

In an example embodiment, UE may identify a BWP identity from DCI tosimplify the indication process. The total number of bits for BWPidentity may depend on the number of bits that may be employed withinthe scheduling DCI (or switching DCI) and the UE minimum BW. The numberof BWPs may be determined by the UE supported minimum BW along with thenetwork maximum BW. For instance, in a similar way, the maximum numberof BWP may be determined by the network maximum BW and the UE minimumBW. In an example, if 400 MHz is the network maximum BW and 50 MHz isthe UE minimum BW, 8 BWP may be configured to the UE which means that 3bits may be needed within the DCI to indicate the BWP. In an example,such a split of the network BW depending on the UE minimum BW may beuseful for creating one or more default BWPs from the network side bydistributing UEs across the entire network BW, e.g., load balancingpurpose.

In an example embodiment, at least 2 DL and 2 UL BWP may be supported bya UE for a BWP adaption. For example, the total number of BWP supportedby a UE may be given by 2<Number of DL/UL BWP≤floor (Network maximumBW/UE minimum DL/UL BW). For example, a maximum number of configuredBWPs may be 4 for DL and UL respectively. For example, a maximum numberof configured BWPs for UL may be 2.

In an example embodiment, different sets of BWPs may be configured fordifferent DCI formats/scheduling types respectively. For example, somelarger BWPs may be configured for non-slot-based scheduling than thatfor slot-based scheduling. If different DCI formats are defined forslot-based scheduling and non-slot-based scheduling, different BWPs maybe configured for different DCI formats. This may provide flexibilitybetween different scheduling types without increasing DCI overhead. The2-bit bitfield may be employed to indicate a BWP among the four for theDCI format. For example, 4 DL BWPs or [2 or 4] UL BWPs may be configuredfor each DCI formats. Same or different BWPs may be configured fordifferent DCI formats.

In an example embodiment, a required maximum number of configured BWPs(may be not comprising the initial BWP) may depend on the flexibilityneeded for a BWP functionality. For example, in the minimal case ofsupporting bandlimited devices, it may be sufficient to be able toconfigure one DL BWP and one UL BWP (or a single DL/UL BWP pair in caseof unpaired spectrum). For example, to support bandwidth adaptation,there may be a need to configure (at least) two DL BWPs and a singleuplink BWP for paired spectrum (or two DL/UL BWP pairs for unpairedspectrum). For example, to support dynamic load-balancing betweendifferent parts of the spectrum, there may be a need to configure one ormore DL (UL) BWPs that jointly cover different parts of the downlink(uplink) carrier. In an example, for dynamic load balancing, it may besufficient with two bandwidth parts. In addition to the two bandwidthparts, two additional bandwidth parts may be needed for bandwidthadaptation. For example, a Maximum number of configured BWPs may be fourDL BWPs and two UL BWPs for a paired spectrum. For example, a Maximumnumber of configured BWPs may be four DL/UL BWP pairs for an unpairedspectrum.

In an example embodiment, UE may monitor for RMSI and broadcast OSIwhich may be transmitted by the gNB within the common search space (CSS)on the PCell. In an example, RACH response and paging control monitoringon the PCell may be transmitted within the CSS. In an example, when a UEis allowed to be on an active BWP configured with UE-specific searchspace (USSS or USS), the UE may not monitor the common search space.

In an example, for a PCell, at least one of configured DL bandwidthparts may comprise at least one CORESET with a CSS type. For example, tomonitor RMSI and broadcast OSI, UE may periodically switch to the BWPcontaining the CSS. In an example, the UE may periodically switch to theBWP containing the CSS for RACH response and paging control monitoringon the PCell.

In an example, if BWP switching to monitor the CSS happens frequently,it may result in increasing overhead. In an example, the overhead due tothe CSS monitoring may depends on overlapping in frequency between anytwo BWPs. In an example, in a nested BWP configuration where one BWP isa subset of another BWP, the same CORESET configuration may be employedacross the BWPs. In this case, unless reconfigured otherwise, a defaultBWP may be the one containing the CSS, and another BWP may contain theCSS. In an example, the BWPs may be partially overlapping. If theoverlapping region is sufficient, a CSS may be across a first BWP and asecond BWP. In an example, two non-overlapping BWP configurations mayexist.

In an example embodiment, there may be one or more benefits ofconfiguring the same CORESET containing the CSS across BWPs. Forexample, RMSI and broadcast OSI monitoring may be handled withoutnecessitating BWP switching. In an example, RACH response and pagingcontrol monitoring on the PCell may also be handled without switching.For example, if CORESET configuration is the same across BWPs,robustness for BWP switching may improve, because even if gNB and UE areout-of-sync as to which BWP is currently active, the DL control channelmay work. In an example, one or more constraints on BWP configurationmay not be too much, considering that BWP may be for power saving, eventhe nested configuration may be very versatile for differentapplications.

In an example embodiment, for the case where the BWP configurations arenon-overlapping in frequency, there may not be spec mandate for UE tomonitor RMSI and broadcast OSI in the CSS. It may be left toimplementation to handle this case.

In an example embodiment, NR may support group-common search space(GCSS). For example, the GCSS may be employed as an alternative to CSSfor certain information. In an example, gNB may configure GCSS within aBWP for a UE, and information such as RACH response and paging controlmay be transmitted on GCSS. For example, the UE may monitor GCSS insteadof switching to the BWP containing the CSS for such information.

In an example embodiment, for pre-emption indication and othergroup-based commands on a serving cell, gNB may transmit the informationon GCSS. UE may monitor the GCSS for the information. For example, forSCell which may not have CSS.

In an example embodiment, NR may configure a CORESET without using aBWP. For example, NR support to configure a CORESET based on a BWP toreduce signaling overhead. In an example, a first CORESET for a UEduring an initial access may be configured based on its default BWP. Inan example, a CORESET for monitoring PDCCH for RAR and paging may beconfigured based on a DL BWP. In an example, the CORESET for monitoringgroup common (GC)-PDCCH for SFI may be configured based on a DL BWP. Inan example, the CORESET for monitoring GC-DCI for pre-emption indicationmay be configured based on a DL BWP. In an example, the BWP index may beindicated in the CORESET configuration. In an example, the default BWPindex may not be indicated in the CORESET configuration.

In an example embodiment, the contention-based random access (CBRA) RACHprocedure may be supported via an initial active DL and UL BWPs sincethe UE identity is unknown to the gNB. In an example, thecontention-free random access (CFRA) RACH procedure may be supported viathe USS configured in an active DL BWP for the UE. For example, in thiscase, an additional CSS for RACH purpose may not need to be configuredper BWP. For example, idle mode paging may be supported via an initialactive DL BWP and the connected mode paging may be supported via adefault BWP. No additional configurations for the BWP for pagingpurposes may not be needed for paging. For the case of pre-emption, aconfigured BWP (on a serving cell) may have the CSS configured formonitoring the pre-emption indications.

In an example embodiment, for a configured DL BWP, a group-common searchspace may be associated with at least one CORESET configured for thesame DL BWP. For example, depending on the monitoring periodicity ofdifferent group-common control information types, it may not bepractical for the UE to autonomously switch to a default BWP where agroup-common search space is available to monitor for such DCI. In thiscase, if there is at least one CORESET configured on a DL BWP, it may bepossible to configure a group-common search space in the same CORESET.

In an example embodiment, a center frequency of the activated DL BWP maynot be changed. In an example, the center frequency of the activated DLBWP may be changed. For example, For TDD, if the center frequency of theactivated DL BWP and deactivated DL BWP is not aligned, the active ULBWP may be switched implicitly.

In an example embodiment, BWPs with different numerologies may beoverlapped, and rate matching for CSI-RS/SRS of another BWP in theoverlapped region may be employed to achieve dynamic resource allocationof different numerologies in FDM/TDM fashion. In an example, for the CSImeasurement within one BWP, if the CSI-RS/SRS is collided with data/RSin another BWP, the collision region in another BWP may be rate matched.For example, CSI information over the two BWPs may be known at a gNBside by UE reporting. Dynamic resource allocation with differentnumerologies in a FDM manner may be achieved by gNB scheduling.

In an example embodiment, PUCCH resources may be configured in aconfigured UL BWP, in a default UL BWP and/or in both. For instance, ifthe PUCCH resources are configured in the default UL BWP, UE may retuneto the default UL BWP for transmitting an SR. for example, the PUCCHresources are configured per BWP or a BWP other than the default BWP,the UE may transmit an SR in the current active BWP without retuning.

In an example embodiment, if a configured SCell is activated for a UE, aDL BWP may be associated with an UL BWP at least for the purpose ofPUCCH transmission, and a default DL BWP may be activated. If the UE isconfigured for UL transmission in same serving cell, a default UL BWPmay be activated.

In an example embodiment, at least one of configured DL BWPs comprisesone CORESET with common search space (CSS) at least in primary componentcarrier. The CSS may be needed at least for RACH response (msg2) andpre-emption indication.

In an example, for the case of no periodic gap for RACH responsemonitoring on Pcell, for Pcell, one of configured DL bandwidth parts maycomprise one CORESET with the CSS type for RMSI & OSI. For Pcell, aconfigured DL bandwidth part may comprise one CORESET with the CSS typefor RACH response & paging control for system information update. For aserving cell, a configured DL bandwidth part may comprise one CORESETwith the CSS type for pre-emption indication and other group-basedcommands.

In an example, for the case of a presence of periodic gap for RACHresponse monitoring on Pcell, for Pcell, one of configured DL bandwidthparts may comprise one CORESET with CSS type for RMSI, OSI, RACHresponse & paging control for system information update. For a servingcell, a configured DL bandwidth part may comprise one CORESET with theCSS type for pre-emption indication and other group-based commands.

In an example embodiment, BWPs may be configured with respect to commonreference point (PRB 0) on a NW carrier. In an example, the BWPs may beconfigured using TYPE1 RA as a set of contiguous PRBs, with PRBgranularity for the START and LENGTH, and the minimum length may bedetermined by the minimum supported size of a CORESET.

In an example embodiment, a CSS may be configured on a non-initial BWPfor RAR and paging.

In an example embodiment, to monitor (group) common channel for RRCCONNECTED UE, an initial DL BWP may comprise control channel for RMSI,OSI and paging and UE switches BWP to monitor such channel. In anexample, a configured DL BWP may comprise control channel for Msg2. Inan example, a configured DL BWP may comprise control channel for SFI. Inan example, a configured DL BWP may comprise pre-emption indication andother group common indicators like power control.

In an example embodiment, a DCI may explicitly indicateactivation/deactivation of BWP.

For example, a DCI without data assignment may comprise an indication toactivate/deactivate BWP. In an example, UE may receive a firstindication via a first DCI to activate/deactivate BWP. In order for theUE to start receiving data, a second DCI with a data assignment may betransmitted by the gNB. A UE may receive the first DCI in a targetCORESET in a target BWP. In an example, until there is CSI feedbackprovided to a gNB, the gNB scheduler may make conservative schedulingdecisions.

In an example, a DCI without scheduling for active BWP switching may betransmitted to measure the CSI before scheduling. It may be taken as animplementation issue of DCI with scheduling, for example, the resourceallocation field may be set to zero, which means no data may bescheduled. Other fields in this DCI may comprise one or more CSI/SRSrequest fields.

In an example embodiment, support for a single scheduling DCI to triggeractive BWP switching may be motivated by dynamic BWP adaptation for UEpower saving during active state (which may comprise ON duration andwhen inactivity timer is running when C-DRX is configured). For example,with a C-DRX enabled, a UE may consume significant amount of powermonitoring PDCCH without decoding any grant. To reduce the powerconsumption during PDCCH monitoring, two BWPs may be configured: anarrower BWP for PDCCH monitoring, and a wider BWP for scheduled data.In such a case, the UE may switch back-and-forth between the narrowerBWP and the wider BWP, depending on the burstiness of the traffic. Forexample, the UE may be revisiting a BWP that it has dwelled onpreviously. For this case, combining a BWP switching indication and ascheduling grant may result in low latency and reduced signallingoverhead for BWP switching.

In an example embodiment, a SCell activation and deactivation maytrigger the corresponding action for its configured BWP. In an example,a SCell activation and deactivation may not trigger the correspondingaction for its configured BWP.

In an example embodiment, a dedicated BWP activation/deactivation DCImay impact a DCI format. For example, a scheduling DCI with a dummygrant may be employed. the dummy grant may be constructed byinvalidating one or some of the fields, for example, the resourceallocation field. In an example, it may be feasible to leverage afallback scheduling DCI format (which contains a smaller payload) toimprove the robustness for BWP DCI signalling, without incurring extrawork on introducing a new DCI format.

In an example embodiment, a DCI with data assignment may comprise anindication to activate/deactivate BWP along with a data assignment. Forexample, a UE may receive a combined data allocation and BWPactivation/deactivation message. For example, a DCI format may comprisea field to indicate BWP activation/deactivation along with a fieldindicating UL/DL grant. In this case, the UE may start receiving datawith a single DCI. In this case, the DCI may need indicate one or moretarget resources of a target BWP. A gNB scheduler may have littleknowledge of the CSI in the target BW and may have to make conservativescheduling decisions.

In an example embodiment, for the DCI with data assignment, the DCI maybe transmitted on a current active BWP and scheduling information may befor a new BWP. For example, there may be a single active BWP. There maybe one DCI in a slot for scheduling the current BWP or schedulinganother BWP. The same CORESET may be employed for the DCI scheduling thecurrent BWP and the DCI scheduling another BWP. For example, to reducethe number of blind decoding, the DCI payload size for the DCIscheduling current BWP and the scheduling DCI for BWP switching may bethe same.

In an example embodiment, to support the scheduling DCI for BWPswitching, a BWP group may be configured by gNB, in which a numerologyin one group may be the same. In an example, the BWP switching for theBWP group may be configured, in which BIF may be present in the CORESETsfor one or more BWPs in the group. For example, scheduling DCI for BWPswitching may be configured per BWP group, in which an active BWP in thegroup may be switched to any other BWP in the group.

In an example, embodiment, a DCI comprising scheduling assignment/grantmay not comprise active-BWP indicator. For a paired spectrum, ascheduling DCI may switch UEs active BWP for the transmission directionthat the scheduling is valid for. For an unpaired spectrum, a schedulingDCI may switch the UEs active DL/UL BWP pair regardless of thetransmission direction that the scheduling is valid for. There may be apossibility for downlink scheduling assignment/grant with “zero”assignment, in practice allowing for switch of active BWP withoutscheduling downlink or uplink transmission

In an example embodiment, a timer-based activation/deactivation BWP maybe supported. For example, a timer for activation/deactivation of DL BWPmay reduce signalling overhead and may enable UE power savings. Theactivation/deactivation of a DL BWP may be based on an inactivity timer(referred to as a BWP inactive (or inactivity) timer). For example, a UEmay start and reset a timer upon reception of a DCI. When the UE is notscheduled for the duration of the timer, the timer may expire. In thiscase, the UE may activate/deactivate the appropriate BWP in response tothe expiry of the timer. For example, the UE may activate for examplethe Default BWP and may deactivate the source BWP.

For example, a BWP inactivity timer may be beneficial for power savingfor a UE switching to a default BWP with smaller BW and fallback for aUE missing DCI based activation/deactivation signaling to switch fromone BWP to another BWP

In an example embodiment, triggering conditions of the BWP inactivitytimer may follow the ones for the DRX timer in LTE. For example, anOn-duration of the BWP inactivity timer may be configured, and the timermay start when a UE-specific PDCCH may be successfully decodedindicating a new transmission during the On-duration. The timer mayrestart when a UE-specific PDCCH is successfully decoded indicating anew transmission. The timer may stop once the UE is scheduled to switchto the default DL BWP.

In an example embodiment, for fallback, the BWP inactivity timer maystart once the UE switches to a new DL BWP. The timer may restart when aUE-specific PDCCH is successfully decoded, wherein the UE-specific PDCCHmay be associated with a new transmission, a retransmission or someother purpose, e.g., SPS activation/deactivation if supported.

In an example embodiment, a UE may switch to a default BWP if the UEdoes not receive any control/data from the network during a BWPinactivity timer running. The timer may be reset upon reception of anycontrol/data. For example, the timer may be triggered when UE receives aDCI to switch its active DL BWP from the default BWP to another. Forexample, the timer may be reset when a UE receives a DCI to schedulePDSCH(s) in the BWP other than the default BWP.

In an example embodiment, a DL BWP inactivity timer may be definedseparately from a UL BWP inactivity timer. For example, there may besome ways to set the timer, e.g., independent timer for DL BWP and ULBWP, or a joint timer for DL and UL BWP. In an example, for the separatetimers, assuming both DL BWP and UL BWP are activated, if there is DLdata and UL timer expires, UL BWP may not be deactivated since PUCCHconfiguration may be affected. For example, for the uplink, if there isUL feedback signal related to DL transmission, the timer may be reset(Or, UL timer may not be set if there is DL data). On the other hand, ifthere is UL data and the DL timer expires, there may be no issue if theDL BWP is deactivated since UL grant is transmitted in the default DLBWP.

In an example embodiment, a BWP inactivity-timer may enable the fallbackto default BWP on Pcell and Scell.

In an example embodiment, a timer-based activation/deactivation of BWPmay be similar to a UE DRX timer. For example, there may not be aseparate inactivity timer for BWP activation/deactivation for the UE DRXtimer. For example, one of the UE DRX inactivity timer may trigger BWPactivation/deactivation.

For example, there may be a separate inactivity timer for BWPactivation/deactivation for the UE DRX timer. For example, the DRXtimers may be defined in a MAC layer, and the BWP timer may be definedin a physical layer. In an example, If the same DRX inactivity timer isemployed for BWP activation/deactivation, UE may stay in a wider BWP foras long as the inactivity timer is running, which may be a long time.For example, the DRX inactivity timer may be set to a large value of100-200 milliseconds for C-DRX cycle of 320 milliseconds, larger thanthe ON duration (10 milliseconds). This may imply that power saving dueto narrower BWP may not be achievable. To realize potential of UE powersaving promised by BWP switching, a new timer may be defined, and it maybe configured to be smaller than the DRX inactivity timer. From thepoint of view of DRX operation, BWP switching may allow UE to operate atdifferent power levels during the active state, effectively providingsome more intermediate operating points between the ON and OFF states.

In an example embodiment, with a DCI explicit activation/deactivation ofBWP, a UE and a gNB may not be synchronized with respect to which BWP isactivated/deactivated. The gNB scheduler may not have CSI informationrelated to a target BWP for channel-sensitive scheduling. The gNB may belimited to conservative scheduling for one or more first severalscheduling occasions. The gNB may rely on periodic or aperiodic CSI-RSand associated CQI report to perform channel-sensitive scheduling.Relying on periodic or aperiodic CSI-RS and associated CQI report maydelay channel-sensitive scheduling and/or lead to signaling overhead(e.g. in the case where we request aperiodic CQI). To mitigate a delayin acquiring synchronization and channel state information, a UE maytransmit an acknowledgement upon receiving an activation/deactivation ofBWP. For example, a CSI report based on the provided CSI-RS resource maybe transmitted after activation of a BWP and is employed asacknowledgment of activation/deactivation.

In an example embodiment, a gNB may provide a sounding reference signalfor a target BWP after a UE tunes to a new bandwidth. In an example, theUE may report the CSI, which is employed as an acknowledgement by thegNB to confirm that the UE receive an explicit DCI command andactivates/deactivates the appropriate BWPs. In an example, for the caseof an explicit activation/deactivation via DCI with data assignment, afirst data assignment may be carried out without a CSI for the targetBWP

In an example embodiment, a guard period may be defined to take RFretuning and the related operations into account. For example, a UE mayneither transmit nor receive signals in the guard period. A gNB may needto know the length of the guard period. For example, the length of theguard period may be reported to the gNB as a UE capability. The lengthof the guard period may be closely related on the numerologies of theBWPs and the length of the slot. For example, the length of the guardperiod for RF retuning may be reported as a UE capability. In anexample, the UE may report the absolute time in vs. in an example, theUE may report the guard period in symbols.

In an example embodiment, after the gNB knows the length of the guardperiod by UE reporting, the gNB may want to keep the time domainposition of guard period aligned between the gNB and the UE. Forexample, the guard period for RF retuning may be predefined for timepattern triggered BWP switching. In an example, for the BWP switchingtriggered by DCI and timer, the guard period for DCI and timer based BWPswitching may be an implementation issue. In an example, for BWPswitching following some time pattern, the position of the guard periodmay be defined. For example, if the UE is configured to switchperiodically to a default BWP for CSS monitoring, the guard period maynot affect the symbols carrying CSS.

In an example embodiment, a single DCI may switch the UE's active BWPform one to another (of the same link direction) within a given servingcell. A separate field may be employed in the scheduling DCI to indicatethe index of the BWP for activation, such that UE may determine thecurrent DL/UL BWP according to a detected DL/UL grant without requiringany other control information. In case the BWP change does not happenduring a certain time duration, the multiple scheduling DCIs transmittedin this duration may comprise the indication to the same BWP. During thetransit time when potential ambiguity may happen, gNB may sendscheduling grants in the current BWP or together in the other BWPscontaining the same target BWP index, such that UE may obtain the targetBWP index by detecting the scheduling DCI in either one of the BWPs. Theduplicated scheduling DCI may be transmitted K times. When UE receiveone of the K times transmissions, UE may switch to the target BWP andstart to receive or transmit (UL) in the target BWP according to the BWPindication field.

In an example embodiment, switching between BWPs may not introduce largetime gaps when UE may not be able to receive due to re-tuning, neitherafter detecting short inactivity (Case 1) or when data activity isreactivated (Case 2). For example, in Case 2, long breaks of severalslots may severely impact the TCP ramp up as UE may not be able totransmit and receive during those slots, impacting obtained RTT and datarate. Case 1 may be seen less problematic at first glance but similarlylong break in reception may make UE out of reach from network point ofview reducing network interest to utilize short inactivity timer.

In an example, if BWP switching takes significant time, and UE requiresnew reference symbols to update AGC, channel estimation etc., the systemmay have less possibilities/motivation to utilize active BWP adaption inthe UE. This may be achieved by preferring configuration where BWPcenter frequency remains the same when switching between BWPs.

In an example embodiment, a frequency location of UE RF bandwidth may beindicated by gNB. For example, considering the UE RF bandwidthcapability, the RF bandwidth of the UE may be usually smaller than thecarrier bandwidth. The supported RF bandwidth for a UE is usually a setof discrete values (e.g., 10 MHz, 20 MHz, 50 MHz and so on), for energysaving purpose, the UE RF bandwidth may be determined as the minimumavailable bandwidth supporting the BWP bandwidth. But the granularity ofBWP bandwidth is PRB level, which is decoupled with UE RF bandwidth andmore flexible. As a result, in most cases the UE RF bandwidth is largerthan the BWP bandwidth. The UE may receive the signal outside thecarrier bandwidth, especially if the configured BWP is configured nearthe edge of the carrier bandwidth. And the inter-system interference orthe interference from the adjacent cell outside the carrier bandwidthmay impact the receiving performance of the BWP. Thus, to keep the UE RFbandwidth in the carrier bandwidth, it is necessary to indicate thefrequency location of the UE RF bandwidth by gNB.

In an example embodiment, in terms of measurement gap configuration, thegap duration may be determined based on the measurement duration andnecessary retuning gap. For example, different retuning gap may beneeded depending on the cases. For example, if a UE does not need toswitch its center, the retuning may be small such as 20 us. For the casethat the network may not know whether the UE needs to switch its centeror not to perform measurement, a UE may indicate the necessary retuninggap for a measurement configuration.

In an example embodiment, the necessary gap may depend on the currentactive BWP which may be dynamically switched via switching mechanism. Inthis case, for example, UEs may need to dynamically indicate thenecessary gap.

In an example embodiment, the measurement gap may be implicitly created,wherein the network may configure a certain gap (which may comprise thesmallest retuning latency, for example, the network may assume smallretuning gap is necessary if both measurement bandwidth and active BWPmay be included within UE maximum RF capability assuming centerfrequency of current active BWP is not changed). In this case, forexample, if a UE needs more gap than the configured, the UE may skipreceiving or transmitting.

In an example embodiment, different measurement gap and retuning latencymay be assumed for RRM and CSI respectively. For CSI measurement, ifperiodic CSI measurement outside of active BWP is configured, a UE mayneed to perform its measurement periodically per measurementconfiguration. For RRM, it may be up to UE implementation where toperform the measurement as long as it satisfies the measurementrequirements. In this case, for example, the worst-case retuning latencyfor a measurement may be employed. In an example, as the retuninglatency may be different between intra-band and inter-band retuning,separate measurement gap configuration between intra-band and inter-bandmeasurement may be considered.

In an example embodiment, for multiple DCI formats with the same DCIsize of a same RNTI, a respective DCI format may comprise an explicitidentifier to distinguish them. For example, a same DCI size may comefrom a few (but not a large number of) zero-padding bits at least inUE-specific search space.

In an example embodiment, when there is a BWP switching, a DCI in thecurrent BWP may need to indicate resource allocation in the next BWPthat the UE is expected to switch. For example, the resource allocationmay be based on the UE-specific PRB indexing, which may be per BWP. Arange of the PRB indices may change as the BWP changes. In an example,the DCI to be transmitted in current BWP may be based on the PRBindexing for the current BWP. The DCI may need to indicate the RA in thenew BWP, which may arouse a conflict. To resolve the conflict withoutsignificantly increasing UEs blind detection overhead, the DCI size andbit fields may not change per BWP for a given DCI type.

In an example embodiment, as the range of the PRB indices may change asthe BWP changes, one or more employed bits among the total bit field forRA may be dependent on the employed BWP. For example, UE may employ theindicated BWP ID that the resource allocation is intended to identifythe resource allocation bit field.

In an example embodiment, a DCI size of the BWP may consider two cases.One case may be a normal DCI detection without BWP retuning, and theother case may be a DCI detection during the BWP retuning.

For example, in some cases, a DCI format may be independent of the BW ofthe active DL/UL BWP (which may be called as fallback DCI). In anexample, at least one of DCI formats for DL may be configured to havethe same size to a UE for one or more configured DL BWPs of a servingcell. In an example, at least one of the DCI formats for UL may beconfigured to have the same size to a UE for one or more configured ULBWPs of a serving cell. In an example embodiment, a BWP-dependent DCIformat may be monitored at the same time (which may be called as normalDCI) for both active DL BWP and active UL BWP. For example, UE may beconfigured to monitor both DCI formats at the same time. During the BWPactivation/deactivation, gNB may assign the fallback DCI format to avoidambiguity during the transition period.

In an example embodiment, if a UE is configured with multiple DL or ULBWPs in a serving cell, an inactive DL/UL BWP may be activated by a DCIscheduling a DL assignment or UL grant respectively in this BWP. As theUE is monitoring the PDCCH on the currently active DL BWP, the DCI maycomprise an indication to a target BWP that the UE may switch to forPDSCH reception or UL transmission. A BWP indication may be inserted inthe UE-specific DCI format for this purpose. The bit width of this fieldmay depend on either the maximum possible or presently configured numberof DL/UL BWPs. Similar to CIF, it may be simpler to set the BWPindication field to a fixed size based on the maximum number ofconfigured BWPs.

In an example, a DCI format size may match the BW of the BWP in whichthe PDCCH is received. To avoid an increase in the number of blinddecodes, the UE may identify the RA field based on the scheduled BWP.For example, for a transition from a small BWP to a larger BWP, the UEmay identify the RA field as being the LSBs of the required RA field forscheduling the larger BWP.

In an example embodiment, a same DCI size for scheduling different BWPsmay be defied by keeping a same size of resource allocation field forone or more configured BWPs. For example, gNB may not be aware ofwhether UE switches BWPs if gNB does not receive at least one responsefrom the UE (e.g., gNB may be aware of if UE switches BWPs based on areception of ACK/NACK from the UE). In an example, to avoid such amismatch between gNB and UE, NR may define fallback mechanism. Forexample, if there is no response from the UE, gNB may transmit thescheduling DCI for previous BWPs and that for newly activated BWP sincethe UE may receive the DCI on either BWP. When the gNB receives aresponse from the UE, the gNB may confirm that the active BWP switchingis completed. In an example, if a same DCI size for scheduling differentBWPs is considered and COREST configuration is also the same fordifferent BWPs, gNB may not transmit multiple DCIs.

In an example embodiment, DCI format(s) may be configureduser-specifically per cell, e.g., not per BWP. For example, after the UEsyncs to the new BWP, the UE may start to monitor pre-configuredsearch-space on the CORESET. If the DCI formats may be configured percell to keep the number of DCI formats, the corresponding header size inDCI may be small.

In an example embodiment, a size of DCI format in different BWPs mayvary and may change at least due to different size of RA bitmap ondifferent BWPs. For example, the size of DCI format configured in a cellfor a UE may be dependent on BWP it schedules.

In an example embodiment, the monitored DCI format size on asearch-space of a CORESET may be configurable with the sufficiently finegranularity (the granularity may be predefined). For example, themonitored DCI format size with sufficient granularity may be beneficialwhen a gNB may have the possibility to set freely the monitoring DCIformat size on a search-spaces of a CORESET, such that it mayaccommodate the largest actual DCI format size variant among one or moreBWPs configured in a serving cell.

In an example embodiment, for a UE-specific serving cell, one or more DLBWPs and one or more UL BWPs may be configured by dedicated RRC for aUE. For the case of PCell, this may be done as part of the RRCconnection establishment procedure. For the SCell, this may be done viaRRC configuration which may indicate the SCell parameters.

In an example embodiment, when a UE receives SCell activation command,there may be a default DL and/or UL BWP which may be activated sincethere may be at least one DL and/or UL BWP which may be monitored by theUE depending on the properties of the SCell (DL only or UL only orboth). This BWP which may be activated upon receiving SCell activationcommand, may be informed to the UE via the a RRC configuration whichconfigured the BWP on this serving cell.

For example, for SCell, RRC signalling for SCellconfiguration/reconfiguration may be employed to indicate which DL BWPand/or which UL BWP may be activated when the SCell activation commandis received by the UE. The indicated BWP may be the initially activeDL/UL BWP on the SCell. Therefore, SCell activation command may activateDL and/or UL BWP.

In an example embodiment, for a SCell, RRC signaling for the SCellconfiguration/reconfiguration may be employed for indicating a defaultDL BWP on the SCell which may be employed for fall back purposes. Forexample, the default DL BWP may be same or different from the initiallyactivated DL/UL BWP which is indicated to UE as part of the SCellconfiguration. In an example, a default UL BWP may be configured to UEfor the case of transmitting PUCCH for SR (as an example), in case thePUCCH resources are not configured in every BWP for the sake of SR.

In an example, a Scell may be for DL only. For the Scell for DL only, UEmay keep monitoring an initial DL BWP (initial active or default) untilUE receives SCell deactivation command.

In an example, a Scell may be for UL only. For the Scell for UL only,when UE receives a grant, UE may transmit on the indicated UL BWP. In anexample, the UE may not maintain an active UL BWP if UE does not receivea grant. In an example, not mainlining the active UL BWP due to no grantreceive may not deactivate the SCell.

In an example, a Scell may be for UL and DL. For the Scell for UL andDL, a UE may keep monitoring an initial DL BWP (initial active ordefault) until UE receives SCell deactivation command and. The UL BWPmay be employed when there is a relevant grant or an SR transmission.

In an example, a BWP deactivation may not result in a SCelldeactivation. For example, when the UE receives the SCell deactivationcommand, the active DL and/or UL BWPs may be considered deactivated.

In an example embodiment, if the SCell has its associated UL and/or a UEis expected to perform RACH procedure on SCell during activation,activation of UL BWP may be needed. For example, at SCell activation, DLonly (only active DL BWP) or DL/UL (both DL/UL active BWP) may beconfigured. Regarding SUL band as a SCell, a UE may select default ULBWP based on measurement or the network configures which one in itsactivation.

In an example embodiment, one or more BWPs are semi-staticallyconfigured via UE-specific RRC signaling. In a CA system, if a UEmaintains RRC connection with the primary component carrier (CC), theBWP in secondary CC may be configured via RRC signaling in the primaryCC.

In an example embodiment, one or more BWPs may be semi-staticallyconfigured to a UE via RRC signaling in PCell. A DCI transmitted inSCell may indicate a BWP among the one or more configured BWP, and grantdetailed resource based on the indicated BWP.

In an example embodiment, for a cross-CC scheduling, a DCI transmittedin PCell may indicate a BWP among the one or more configured BWPs, andgrants detailed resource based on the indicated BWP.

In an example embodiment, when a SCell is activated, a DL BWP may beinitially activated for configuring CORESET for monitoring the firstPDCCH in Scell. The DL BWP may serve as a default DL BWP in the SCell.In an example, since the UE performs initial access via a SS block inPCell, the default DL BWP in SCell may not be derived from SS block forinitial access. The default DL BWP in Scell may be configured by RRCsignaling in the PCell.

In an example embodiment, when an Scell is activated, an indicationindicating which DL BWP and/or which UL BWP are active may be in RRCsignalling for Scell configuration/reconfiguration. For example, the RRCsignalling for Scell configuration/reconfiguration may be employed forindicating which DL BWP and/or which UL BWP are initially activated whenthe Scell is activated.

In an example embodiment, when an Scell is activated, an indicationindicating which DL BWP and/or which UL BWP are active may be in Scellactivation signaling. For example, Scell activation signaling may beemployed for indicating which DL BWP and/or which UL BWP are initiallyactivated when the Scell is activated.

In an example embodiment, for PCells and pSCells, an initial defaultbandwidth parts for DL and UL (e.g., for RMSI reception and PRACHtransmission) may be valid until at least one bandwidth part isconfigured for the DL and UL via RRC UE-specific signaling,respectively, at what time the initial default DL/UL bandwidth parts maybecome invalid and new default DL/UL bandwidth parts may take effect. Inan example, for an Scell, the SCell configuration may comprise defaultDL/UL bandwidth parts

In an example embodiment, an initial BWP on Pcell may be defined by MIB.In an example, an initial BWP and default BWP may be separatelyconfigurable for the Scell. For an Scell if the Scell is activated, aninitial BWP may be the widest configured BWP of the Scell. For example,after the traffic burst is served, and an inactivity timer expires, a UEmay retune to default BWP which may be the narrow BWP, for powersavings, keeping the Scell active and may be ready to be opened brisklywhen additional data burst arrives.

In an example embodiment, a BWP on Scell may be activated by means ofcross-cell scheduling DCI, if cross-cell scheduling is configured to aUE. In this case, the gNB may activate a BWP on the Scell by indicatingCIF and BWPI in the scheduling DCI.

In an example embodiment, UE and/or gNB may perform synchronizationtracking within an active DL BWP without SS block. For example, TRSalong with DL BWP configuration may be configured. For example, a DL BWPwith SS block or TRS may be configured as a reference forsynchronization tracking, which may be similar to the design of CSSmonitoring when the BWP does not comprise a common CORESET.

In an example embodiment, SS-block based RRM measurements may bedecoupled with BWP framework. For example, measurement configurationsfor each RRM and CSI feedback may be independently configured frombandwidth part configurations. CSI and SRS measurements/transmissionsmay be performed within the BWP framework.

In an example embodiment, for a MCS assignment of the first one or moreDL data packets after active DL BWP switching, the network may assignrobust MCS to a UE for the first one or more DL data packets based onRRM measurement reporting. In an example, for a MCS assignment of thefirst one or more DL data packets after active DL BWP switching, thenetwork may signal to a UE by active DL BWP switching DCI to triggeraperiodic CSI measurement/reporting to speed up link adaptationconvergence. For a UE, periodic CSI measurement outside the active BWPin a serving cell may not supported. For a UE, RRM measurement outsideactive BWP in a serving cell may be supported. For a UE, RRM measurementoutside configured BWPs in a serving cell may be supported.

In an example embodiment, the RRM measurements may be performed on a SSBand/or CSI-RS. The RRM/RLM measurements may be independent of BWPs.

In an example embodiment, UE may not be configured with aperiodic CSIreports for non-active DL BWPs. For example, the CSI measurement may beobtained after the BW opening and the wide-band CQI of the previous BWPmay be employed as starting point for the other BWP on the NW carrier.

In an example embodiment, UE may perform CSI measurements on the BWPbefore scheduling. For example, before scheduling on a new BWP, the gNBmay intend to find the channel quality on the potential new BWPs beforescheduling the user on that BWP. In this case, the UE may switch to adifferent BWP and measure channel quality on the BWP and then transmitthe CSI report. There may be no scheduling needed for this case.

FIG. 25 shows example of BWP switching associated with BWP inactivitytimer. A UE may receive RRC message comprising parameters of at leastone SCell and one or more BWP configuration associated with the at leastone SCell. Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1 in the figure), one BWPas the default BWP (e.g., BWP 0 in the figure). The UE may receive a MACCE to activate the Scell at the n^(th) subframe. The UE may start thesCellDeactivationTimer, and start reporting CSI for the SCell, and/orstart reporting CSI for the first active BWP of the SCell at the(n+8)^(th) subframe. The UE may start the BWP inactivity timer whenreceiving a DCI indicating switching BWP from BWP 1 to BWP 2, at the(n+8+k)^(th) subframe. The gap k between receiving the DCI and startingthe BWP inactivity timer may be configured or predefined, to allow theUE switch to the new BWP. When receiving a PDCCH indicating DLscheduling on BWP 2, for example, at the (n+8+k+m)^(th) subframe, the UEmay restart the BWP inactivity timer. The UE may switch back to thedefault BWP (0) when the BWP inactivity timer expires, at the(n+8+k+m+1)^(th) subframe. The UE may deactive the SCell when thesCellDeactivationTimer expires. Employing the BWP inactivity timer mayfurther reduce UE's power consumption when the UE is configured withmultiple cells with each cell having wide bandwidth (e.g., 1 GHz). TheUE may only transmit on or receive from a narrow-bandwidth BWP (e.g., 5MHz) on the PCell or SCell when there is no activity on an active BWP.

In an example, a UE may receive one or more RRC messages configuring afirst active BWP and a default BWP for a SCell. These two BWPs may bedifferent, for example, as shown in FIG. 25, the first active BWP is BWP0, and the default BWP is BWP 1. When receiving a MAC CE activating theSCell, the UE may activate the first active BWP (BWP 1), e.g., bymonitoring one or more PDCCH and/or transmitting uplink signals on thefirst active DL or UL BWP. In an example, the UE may stay on the firstactive BWP (BWP 1) until receiving a DCI indicating active BWP change,and starting the BWP inactivity timer. In this case, it may be not powerefficient, since the UE may keep monitoring the PDCCH on the firstactive BWP, even though there may be no activity on the first active BWPuntil receiving a DCI indicating a BWP change. It's necessary to havemechanism to reduce the power consumption for a UE when a SCellactivated with multiple BWPs.

FIG. 26 shows an example of the embodiment. A UE may receive one or moreRRC message comprise at least configuration parameters of a plurality ofcells, the plurality of cells comprising a PCell and at least one SCell.The configuration parameters of the at least one SCell may comprise atleast one of: one or more BWPs associated with one or more radioresource configuration (e.g., frequency location, bandwidth, subcarrierspacing, cyclic prefix, one or more CSI-RS resource configuration); atleast a first BWP identifier indicating a first active BWP; a second BWPidentifier indicating a default BWP; a BWP inactivity timer with a timervalue; a SCell deactivation timer with a timer value. The BWP inactivitytimer value may be configured per cell or per base station in a RRCmessage, or may be a pre-defined value. The SCell deactivation timer maybe configured for each SCell with a different/same value. In an example,the SCell deactivation timer may be configured for all SCells with asame value in a RRC message, or as a pre-defined value. The UE mayreceive a SCell activation/deactivation MAC CE comprising parametersindicating activation or deactivation of the at least one SCell at then^(th) subframe. In an example, a UE may receive a SCellactivation/deactivation DCI indicating activation or deactivation of theat least one SCell at the n^(th) subframe. The UE may start or restartthe SCell deactivation timer at the (n+k)^(th) subframe, in response toreceiving the SCell activation/deactivation MAC CE or DCI. In anexample, the UE may start the BWP inactivity timer at the (n+k+m)^(th)subframe, in response to receiving the SCell activation/deactivation MACCE or DCI, if the first active BWP is different from the default BWP. Inan example, the UE may start CSI report for the first active BWP at the(n+k)^(th) subframe. In another example, the UE may start CSI report forthe first active BWP at the (n+k+m)^(th) subframe. The first time offset(e.g., k value) between receiving the SCell activation/deactivation MACCE or DCI and starting the SCell deactivation timer may be configured ina RRC message, or preconfigured as a fixed value. The second time offset(e.g., m value) between starting the SCell deactivation timer andstarting the BWP inactivity timer may be configured in a RRC message, orpredefined as a fixed value. For example, the first time offset may beconfigured as zero if a DCI is used to activate a SCell in case that aUE is capable of activating the SCell quickly. The second time offsetmay be predefined or configured as zero if the time for SCell activationis same as the time for BWP activation, then the UE may start the SCelldeactivation timer and BWP inactivity timer (if the first active BWP isdifferent from the default BWP) in the same time. With the embodiment,when activating a SCell with multiple BWPs, the UE may switch to thedefault BWP when the BWP inactivity timer expires, even withoutreceiving a DCI indicating BWP change, therefore reducing the powerconsumption. The configurable or predefined time offset for SCellactivation and BWP activation may give the gNB more flexibility oncontrolling SCell activation and BWP activation, and allow different UEswith different capability (e.g., on BWP switch) to change BWP correctly.

In an example, when receiving a second DCI indicating an active BWPchange, a UE may start or restart the BWP inactivity timer depending onwhether the new active BWP is the default BWP. For example, in FIG. 26,a UE may receive the second DCI indicating active BWP change from BWP 1to BWP 2, at the (n+k+m+l)^(th) subframe. The UE may start or restartthe BWP timer if the new active BWP is not the default BWP. In somecase, when the UE may have a quick BWP switch, the UE may start orrestart the BWP inactivity timer at the same subframe, i.e., the(n+k+m+l)^(th) subframe. In another example, when the UE may have a slowBWP switch, the UE may start or restart the BWP inactivity timer at the(n+k+m+l+o)^(th) subframe. The time offset (e.g., o value) betweenreceiving the second DCI and starting BWP inactivity timer may beconfigured or predefined. The time offset may be a transition gap. Thetransition gap may be a time period between a first time when receivingthe second DCI and a second time when the wireless device completes BWPswitching from BWP 1 to BWP 2. With the configurable time offset betweenreceiving BWP change DCI and starting the BWP inactivity timer, it maygive the gNB more flexibility on controlling BWP change, and allowdifferent UEs with different capability (e.g., on BWP switch) to changeBWP correctly.

In an example, a UE may receive the second DCI indicating active BWPchange from an active BWP to a default BWP, for example, in FIG. 26, aUE may receive the second DCI indicating active BWP change from BWP 1 toBWP 0. The UE may stop the BWP inactivity timer, in response toreceiving the second DCI. With the embodiment, stopping the BWPinactivity timer when switching an active BWP to the default BWP mayavoid unnecessary BWP inactivity timer management at the gNB and the UE.

FIG. 27 shows an example of the embodiment. A UE may receive, from abase station, one or more RRC message comprise at least configurationparameters of a cell. The configuration parameters of the cell maycomprise at least one of: one or more BWPs associated with one or moreradio resource configuration (e.g., frequency location, bandwidth,subcarrier spacing, cyclic prefix, one or more CSI-RS resourceconfiguration); at least a first BWP identifier indicating a firstactive BWP; a second BWP identifier indicating a default BWP; a BWPinactivity timer with a timer value. In an example, the UE maycommunicate with the base station via the first active BWP (e.g., BWP 1in FIG. 27). The UE may receive a first DCI indicating an active BWPswitching from the first active BWP to a second BWP (e.g., BWP 2 in FIG.27) at slot n. The wireless device may finish the active BWP switchingin a transition gap (with a length k, as shown FIG. 27) in response tothe first DCI. The wireless device may start the BWP inactivity timer atslot n+k. During the BWP inactivity timer being running, the wirelessdevice may monitor a PDCCH on the second BWP which is an active BWPafter the active BWP switching. The wireless device may receive a secondDCI indicating an active BWP switching from the second BWP to thedefault BWP. In response to the second DCI, the wireless device may stopthe BWP inactivity timer at the same slot when receiving the second DCI.In response to the second DCI, the wireless device may stop the BWPinactivity timer at a second slot the transition gap after a first slotwhen receiving the second DCI.

FIG. 28 shows an example of flowchart of the embodiment. At 2810, awireless device may receive one or more messages comprisingconfiguration parameters of a first active BWP and a default BWP of acell. At 2820, the wireless device may activate the first active BWP ofthe cell in response to at least one of: activation of the cell;receiving a DCI indicating downlink assignment or uplink grant. At 2830,the wireless device may transmit or receive data packets on the firstactive BWP in response to activating the first active BWP. At 2840, thewireless device may receive a first DCI indicating an active BWPswitching to a second BWP at a first slot. At 2850, in response to thefirst DCI, the wireless device may switch to the second BWP as theactive BWP and start a BWP inactivity timer at a second slot. At 2860,the wireless device may receive a second DCI indicating switching to thedefault BWP as the active BWP. At 2870, in response to the second DCI,the wireless device may switch to the default BWP and stop the BWPinactivity timer.

In an example, a wireless device may receive one or more RRC messagecomprising: configuration parameters of a plurality of cells, theplurality of cells comprising a primary cell and at least one secondarycell, wherein configuration parameters of the at least one secondarycell comprising at least one of: one or more BWPs associated with one ormore radio resource configuration (e.g., frequency location, bandwidth,subcarrier spacing, cyclic prefix, one or more CSI-RS resourceconfiguration); a first active BWP from the one or more BWPs; a defaultBWP from the one or more BWPs; and a timer value for a first BWPinactivity timer. The wireless device may receive a MAC CE or DCIactivating/deactivating the at least one secondary cell. The wirelessdevice may start the first BWP inactivity timer, in response toreceiving the MAC CE or DCI, if the first active BWP is different fromthe default BWP, for the at least one secondary cell. In an example, thewireless device may start the first BWP inactivity timer after apredefined time offset, or a configured time offset. In another example,the wireless device may not start the first BWP inactivity timer, if thefirst active BWP is same as the default BWP.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, a corenetwork device, and/or the like, may comprise one or more processors andmemory. The memory may store instructions that, when executed by the oneor more processors, cause the device to perform a series of actions.Embodiments of example actions are illustrated in the accompanyingfigures and specification. Features from various embodiments may becombined to create yet further embodiments.

FIG. 29 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 2910, a wireless device may receive from a base station,one or more messages comprising configuration parameters of a cell. Theconfiguration parameters may comprise bandwidth part (BWP) parameters ofa first BWP and a second BWP. The configuration parameters may comprisea timer value associated with a BWP inactivity timer. At 2920, a firstdownlink control information may be received at a first slot. The firstdownlink control information may indicate switching to the second BWP asan active BWP. At 2930, in response to the first downlink controlinformation, the first BWP may switch to the second BWP as the activeBWP. In response to the first downlink control information, the BWPinactivity timer may be started at a second slot based on the timervalue. The second slot may occur after the first slot by an amount oftime determined based on a time offset value. At 2940, a default BWP maybe switched to in response to an expiry of the BWP inactivity timer.

According to an example embodiment, the time offset value may beindicated in the configuration parameters. According to an exampleembodiment, the time offset value may be a fixed value. According to anexample embodiment, the cell may be a primary cell of a plurality ofcells. According to an example embodiment, the cell may be a secondarycell of a plurality of cells. According to an example embodiment, theBWP parameters of the first BWP or the second BWP indicate at least oneof: a frequency location; a bandwidth; a value of subcarrier spacing; acyclic prefix; or one or more reference signal resource configuration.

According to an example embodiment, the first BWP may be activated inresponse to receiving a second downlink control information indicating adownlink assignment or an uplink grant. According to an exampleembodiment, the BWP inactivity timer may be started in response to thesecond downlink control information. According to an example embodiment,the first BWP may be activated in response to receiving a commandindicating an activation of the cell. According to an exampleembodiment, the command may be a medium access control control element.According to an example embodiment, the command may be a downlinkcontrol information. According to an example embodiment, the BWPinactivity timer may be started based on the timer value in response tothe command. According to an example embodiment, the activation of thefirst BWP may comprise monitoring a downlink control channel on thefirst BWP. According to an example embodiment, switching from the firstBWP to the second BWP as the active BWP may comprise stopping monitoringa first downlink control channel on the first BWP. According to anexample embodiment, switching from the first BWP to the second BWP asthe active BWP may comprise monitoring a second downlink control channelon the second BWP.

According to an example embodiment, a second downlink controlinformation may be received at a third slot. The second downlink controlinformation may indicate switching to a default BWP as the active BWP.According to an example embodiment, in response to the second downlinkcontrol information, the active BWP may be switched to the default BWP.According to an example embodiment, in response to the second downlinkcontrol information, the BWP inactivity timer may be stopped.

According to an example embodiment, the default BWP may be differentfrom the second BWP. According to an example embodiment, the switchingof the active BWP to the default BWP may comprise monitoring a downlinkcontrol channel on the default BWP. According to an example embodiment,the stopping the BWP inactivity timer may comprise stopping the BWPinactivity timer at the third slot. According to an example embodiment,the time offset value may be based on a capability of the wirelessdevice. According to an example embodiment, a first bandwidth of thefirst BWP may be less than a second bandwidth of the cell. According toan example embodiment, the BWP inactivity timer may be stopped inresponse to receiving a command indicating a deactivation of the cell.

FIG. 30 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3010, a wireless device may receive from a base station,one or more messages comprising configuration parameters of a cell. Theconfiguration parameters may comprise bandwidth part (BWP) parameters ofa first BWP, a default BWP; and a value associated with a BWP inactivitytimer. At 3020, a first downlink control information (DCI) indicatingdownlink assignments may be received. An uplink grant on the first BWPmay be received. At 3030, the BWP inactivity timer may be started withthe value in response to the first DCI. At 3040, a second DCI indicatingswitching an active BWP from the first BWP to the default BWP may bereceived. At 3050, the active BWP may be switched to the default BWP inresponse to the second DCI. The BWP inactivity timer may be stopped inresponse to the second DCI.

FIG. 31 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3110, a wireless device may receive from a base station,one or more messages comprising configuration parameters of bandwidthparts (BWPs) a cell. The configuration parameters may indicate: a firstBWP identifier indicating a first active BWP; a second BWP identifierindicating a default BWP; and a value for a BWP inactivity timer. At3120, a command indicating an activation of the cell may be received. At3130, in response to the command, the BWP inactivity timer may bestarted with the value. At 3140, a downlink control channel may monitorthe first active BWP for a downlink control information while the BWPinactivity timer is running. At 3150, the wireless device may switch tothe default BWP in response to an expiry of the BWP inactivity timer.According to an example embodiment, the command may comprise a mediumaccess control control element. According to an example embodiment, thecommand may comprise a downlink control information.

FIG. 32 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3210, a wireless device may receive from a base station,one or more messages comprising configuration parameters of bandwidthparts (BWPs) a cell. The configuration parameters may indicate: a firstBWP identifier indicating a first active BWP; a second BWP identifierindicating a default BWP; and a time value. At 3210, a commandindicating an activation of the cell may be received. At 3210,monitoring a downlink control channel may be monitored for a downlinkcontrol information on the first active BWP. At 3210, the wirelessdevice may switch to the default BWP in response to a period of timestarting from the receiving the command. The period of time may be basedon the time value.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” or “one or more.” Similarly, any term thatends with the suffix “(s)” is to be interpreted as “at least one” or“one or more.” In this disclosure, the term “may” is to be interpretedas “may, for example.” In other words, the term “may” is indicative thatthe phrase following the term “may” is an example of one of a multitudeof suitable possibilities that may, or may not, be employed to one ormore of the various embodiments. If A and B are sets and every elementof A is also an element of B, A is called a subset of B. In thisspecification, only non-empty sets and subsets are considered. Forexample, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and{cell1, cell2}. The phrase “based on” is indicative that the phrasefollowing the term “based on” is an example of one of a multitude ofsuitable possibilities that may, or may not, be employed to one or moreof the various embodiments. The phrase “in response to” is indicativethat the phrase following the phrase “in response to” is an example ofone of a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments. The terms“including” and “comprising” should be interpreted as meaning“including, but not limited to”.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (Information elements: IEs) may compriseone or more objects, and each of those objects may comprise one or moreother objects. For example, if parameter (IE) N comprises parameter (IE)M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) Kcomprises parameter (information element) J, then, for example, Ncomprises K, and N comprises J. In an example embodiment, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).

Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters of a cell, the configuration parameterscomprising: bandwidth part (BWP) parameters of: a first BWP and adefault BWP; a first timer value associated with a cell deactivationtimer; and a second timer value associated with a BWP inactivity timer;receiving a downlink control information (DCI) indicating an activationof the cell; in response to the DCI: activating the cell; and startingthe cell deactivation timer based on the first timer value; activating,in response to activating the cell, the first BWP of the cell; startingthe BWP inactivity timer based on the second timer value; and inresponse to expiry of the BWP inactivity timer, switching from the firstBWP to the default BWP as an active BWP.
 2. The method of claim 1,wherein the cell is a secondary cell of a plurality of cells.
 3. Themethod of claim 1, wherein the BWP parameters of the first BWP or thedefault BWP indicate at least one of: a frequency location; a bandwidth;a value of subcarrier spacing; a cyclic prefix; or one or more referencesignal resource configurations.
 4. The method of claim 1, wherein theswitching from the first BWP to the default BWP comprises monitoring adownlink control channel on the default BWP.
 5. The method of claim 1,wherein the wireless device starts the BWP inactivity timer in responseto receiving the DCI indicating the activation of the cell.
 6. Themethod of claim 1, further comprising deactivating the cell in responseto at least one of: an expiry of the cell deactivation timer; andreceiving a second DCI indicating a deactivation of the cell.
 7. Themethod of claim 6, further comprising stopping the BWP inactivity timerin response to the deactivating the cell.
 8. The method of claim 1,wherein activating the first BWP comprises monitoring a downlink controlchannel on the first BWP.
 9. The method of claim 8, further comprisingreceiving a second DCI indicating a downlink assignment or an uplinkgrant on the first BWP.
 10. The method of claim 9, further comprising,in response to receiving the second DCI: restarting the BWP inactivitytimer; and restarting the cell deactivation timer.
 11. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive configuration parameters of a cell, the configurationparameters comprising: bandwidth part (BWP) parameters of: a first BWPand a default BWP; a first timer value associated with a celldeactivation timer; and a second timer value associated with a BWPinactivity timer; receive a downlink control information (DCI)indicating an activation of the cell; in response to the DCI: activatethe cell; and start the cell deactivation timer based on the first timervalue; activate, in response to the activation of the cell, the firstBWP of the cell; start the BWP inactivity timer based on the secondtimer value; and in response to expiry of the BWP inactivity timer,switch from the first BWP to the default BWP as an active BWP.
 12. Thewireless device of claim 11, wherein the cell is a secondary cell of aplurality of cells.
 13. The wireless device of claim 11, wherein the BWPparameters of the first BWP or the default BWP indicate at least one of:a frequency location; a bandwidth; a value of subcarrier spacing; acyclic prefix; or one or more reference signal resource configurations.14. The wireless device of claim 11, wherein the switch from the firstBWP to the default BWP comprises monitoring a downlink control channelon the default BWP.
 15. The wireless device of claim 11, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to start the BWP inactivity timer in response toreception of the DCI indicating the activation of the cell.
 16. Thewireless device of claim 11, wherein the instructions, when executed bythe one or more processors, further cause the wireless device todeactivate the cell in response to at least one of: an expiry of thecell deactivation timer; and reception of a second DCI indicating adeactivation of the cell.
 17. The wireless device of claim 16, whereinthe instructions, when executed by the one or more processors, furthercause the wireless device to stop the BWP inactivity timer in responseto the deactivation of the cell.
 18. The wireless device of claim 11,wherein the instructions, when executed by the one or more processors,further cause the wireless device to receive a second DCI indicating adownlink assignment or an uplink grant on the first BWP.
 19. Thewireless device of claim 18, wherein the instructions, when executed bythe one or more processors, further cause the wireless device, inresponse to receiving the second DCI, to: restart the BWP inactivitytimer; and restart the cell deactivation timer.
 20. A system comprising:a base station; and a wireless device comprising: one or moreprocessors; and memory storing instructions that, when executed by theone or more processors, cause the wireless device to: receive, from thebase station, configuration parameters of a cell, the configurationparameters comprising: bandwidth part (BWP) parameters of: a first BWPand a default BWP; a first timer value associated with a celldeactivation timer; and a second timer value associated with a BWPinactivity timer; receive a downlink control information (DCI)indicating an activation of the cell; in response to the DCI: activatethe cell; and start the cell deactivation timer based on the first timervalue; activate, in response to the activation of the cell, the firstBWP of the cell; start the BWP inactivity timer based on the secondtimer value; and in response to expiry of the BWP inactivity timer,switch from the first BWP to the default BWP as an active BWP.